Thank you for the update! 🎉

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 10-15 business days.

Greptile Summary

This PR fixes a JS heap out-of-memory crash on first launch by replacing useCachedPromise (from @raycast/utils) with a hand-rolled stale-while-revalidate pattern using React's useState/useEffect and Raycast's built-in Cache API. The change reduces peak memory during initial data load from ~82 MB to ~22 MB, addressing a real crash for first-time users.

Key changes:

• useModelsData.ts: New implementation reads from Cache synchronously on mount, renders immediately with stale data, then fetches fresh data in the background — mirroring the original keepPreviousData behavior with far lower memory overhead.
• package.json / package-lock.json: @raycast/utils and its dequal transitive dependency removed.
• CHANGELOG.md: New entry added at the top with correct {PR_MERGE_DATE} placeholder.
• .gitignore: Local development artifacts (.claude/, GITHUB_ISSUE.md) excluded from version control.

The implementation is logically sound. Two minor style nits: a placeholder issues/XXX URL in a comment should be updated to the real issue number (65), and a setIsLoading(true) call inside the effect is redundant since isLoading is already initialized to true in that code path.

Confidence Score: 5/5

Safe to merge — all remaining findings are P2 style nits with no impact on correctness or behavior.

The core logic is correct: the stale-while-revalidate semantics are preserved, error handling is appropriate, the fetchedRef guard correctly prevents double-fetching in React StrictMode, and the cache write is deliberately deferred after state update to minimize peak heap. Only two minor style issues remain (a stale placeholder URL and a redundant state setter), neither of which affects runtime behavior.

No files require special attention.

Important Files Changed

This is a comment left during a code review.
Path: extensions/models-dev/src/hooks/useModelsData.ts
Line: 13-14

Comment:
**Placeholder issue URL not updated**

The comment references `issues/XXX` which is a placeholder. Based on the PR description, the actual filed issue is `https://github.com/raycast/utils/issues/65`. This should be updated to point to the real issue for future maintainers.

```suggestion
 * Uses direct fetch + Cache API instead of useCachedPromise to avoid
 * memory spikes during fresh cache population. See:
 * https://github.com/raycast/utils/issues/65
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: extensions/models-dev/src/hooks/useModelsData.ts
Line: 29-42

Comment:
**Redundant `setIsLoading(true)` call**

`isLoading` is already initialized to `!data` on line 29, so when `shouldRevalidate` is `false` (i.e. `data` is `null`), `isLoading` is already `true`. The `setIsLoading(true)` call inside the `if (!shouldRevalidate)` block is a no-op on first render and triggers an unnecessary re-render in React StrictMode (where the effect body runs twice).

```suggestion
  const [isLoading, setIsLoading] = useState(!data);
  const fetchedRef = useRef(false);

  useEffect(() => {
    // Already have cached data or already fetching
    if (fetchedRef.current) return;
    fetchedRef.current = true;

    // If we have cached data, still revalidate in background
    const shouldRevalidate = !!data;
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "Update models-dev extension" | Re-trigger Greptile}

@0xdhrv @pernielsentikaer This one should be relatively straightforward.

Published to the Raycast Store:
https://raycast.com/carlesandres/models-dev

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.